|
|
Noticeable bad performance by WebsydianExpress when installed on Windows or if the Websydian Web Server Component is deployed on a Windows platform.
Noticeable bad performance by applications developed for Windows and using the Websydian Distributed Architecture (DWA).
Looking into the Websydian Web Server Component log you will notice that processing of GETVAL requests takes considerable amount of time.
For some reason the Microsoft Windows platform behaves differently when it comes to handling ACK packages on the TCP protocol level.
This has been reported by several different software packages and on top of that Windows 2008 also includes specific network properties that have been enabled by default by Microsoft. In some environments these properties are not fully functional.
Depending on your version of Windows perform the following changes on both your Web Server and your Application Server. Application Server is where your WebsydianExpress is started using the Start WebsydianExpress or STRAS commands.
These options are for advanced users only. Incorrectly editing the registry can severely damage your system. You should always back up (export or copy) the registry before you make any changes to it.
Some network issues are related to the network driver/card trying to auto negotiate the best speed, in some cases this is not the best approach and will result in a major degradation in speed.
Check your network speed by downloading the free edition of the LanSpeedTest tool (use Google to locate file to download). If the LanSpeedTest tool reports a poor performance try changing your network driver from Auto negotiate speed to a specific speed. Please note depending on your network architecture you might need to tyr out the different speeds and duplex settings available for your network driver.
Use the LanSpeedTest tool to verify your progress as you change the speed setting.
The network speed settings are located under the Advanced tab of your network controller properties under network settings in the control panel.
Add or change the following registry value of the sub key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{Interface GUID}*
* {Interface GUID} is different for every system - locate the interface by verifying the ip/address associated with the interface.
| Value name | Value data type | Value data | Description |
|---|---|---|---|
| TcpAckFrequency | DWORD | 1 | TCP/IP can be the source of some significant remote method
delays. Your can increase TCP performance by immediately acknowledging incoming TCP segments, in all situations. |
Remember to reboot your system after making the registry changes.
Add or change the following registry value of the sub key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{Interface GUID}*
* {Interface GUID} is different for every system - locate the interface by verifying the ip/address associated with the interface.
| Value name | Value data type | Value data | Description |
|---|---|---|---|
| TcpAckFrequency | DWORD | 1 | TCP/IP can be the source of some significant remote method
delays. Your can increase TCP performance by immediately acknowledging incoming TCP segments, in all situations. |
Remember to reboot your system after making the registry changes.
Add or change the following registry value of the sub key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{Interface GUID}*
* {Interface GUID} is different for every system - locate the interface by verifying the ip/address associated with the interface.
| Value name | Value data type | Value data | Description |
|---|---|---|---|
| TcpAckFrequency | DWORD | 1 | TCP/IP can be the source of some significant remote method
delays. Your can increase TCP performance by immediately acknowledging incoming TCP segments, in all situations. |
Open a command prompt and execute the following command. Make sure you run the command prompt as administrator.
The default level is "normal". The possible settings include:
Remember to reboot your system after making the registry and network changes.
If you currently do not have IP/v6 configured in your network we recommend that you disable IP/v6.
Add or change the following registry value of the sub key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TCPIP6\Parameters
| Value name | Value data type | Value data | Description |
|---|---|---|---|
| DisabledComponents | DWORD | Hexadecimal 20 | To use IPv4 instead of IPv6 in prefix policies |
Remember to reboot your system after making the registry changes.
Online documentation - Websydian v6.5